System and method for rendering presentation pages based on locality

ABSTRACT

A system renders presentation pages such as in a wireless communications system. A server includes an extensible stylesheet transformation (XSLT) module. A storage medium contains at least one of images and text. The XSLT module is operative for calling an XSL extension and rendering the at least one of images and text into a presentation page based on a language requirement at a foreign locale.

FIELD OF THE INVENTION

The present invention relates to the field of communications systems,and, more particularly, to electronic mail (email) communicationssystems and related methods.

BACKGROUND OF THE INVENTION

Electronic mail (email) has become an integral part of business andpersonal communications. As such, many users have multiple emailaccounts for work and home use. Moreover, with the increasedavailability of mobile cellular and wireless local area network (LAN)devices that can send and receive emails, many users wirelessly accessemails from mailboxes stored on different email storage servers (e.g.,corporate email storage server, Yahoo, Hotmail, AOL, etc.).

Yet, email distribution and synchronization across multiple mailboxesand over wireless networks can be quite challenging, particularly whenthis is done on a large scale for numerous users. For example, differentemail accounts may be configured differently and with non-uniform accesscriteria. Moreover, as emails are received at the wirelesscommunications device, copies of the emails may still be present in theoriginal mailboxes, which can make it difficult for users to keep theiremail organized.

One particularly advantageous “push” type email distribution andsynchronization system is disclosed in U.S. Pat. No. 6,779,019 toMousseau et al., which is assigned to the present Assignee and is herebyincorporated herein by reference. This system pushes user-selected dataitems from a host system to a user's mobile wireless communicationsdevice upon detecting the occurrence of one or more user-defined eventtriggers. The user may then move (or file) the data items to aparticular folder within a folder hierarchy stored in the mobilewireless communications device, or may execute some other systemoperation on a data item. Software operating at the device and the hostsystem then synchronizes the folder hierarchy of the device with afolder hierarchy of the host system, and any actions executed on thedata items at the device are then automatically replicated on the samedata items stored at the host system, thus eliminating the need for theuser to manually replicate actions at the host system that have beenexecuted at the mobile wireless communications device.

The foregoing system advantageously provides great convenience to usersof wireless email communication devices for organizing and managingtheir email messages. Yet, further convenience and efficiency featuresmay be desired in email distribution and synchronization systems asemail usage continues to grow in popularity. Efficiency would beincreased in transforming application data into presentationinformation. More particularly, some WAP or HTML output could be basedon user locale specially when different templates could be used fordifferent languages. Localized versions of pages in a different languagecould be rendered and information could be passed back to reconcile fordifferent languages in the email system. Commonly assigned U.S. patentapplication Ser. No. 60/720,899 filed Sep. 27, 2005 permits anextensible stylesheet transformation (XSLT) module to render images andtext, but greater control based on locale is desired.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects, features and advantages of different embodiments willbecome apparent from the detailed description which follows, whenconsidered in light of the accompanying drawings in which:

FIG. 1 is schematic block diagram of a direct access electronic mail(email) distribution and synchronization system.

FIG. 2 is a schematic block diagram of an exemplary embodiment of userinterface components of the direct access proxy of the system of FIG. 1.

FIG. 3 is a schematic block diagram of an exemplary embodiment of theWeb client engine of the system of FIG. 1.

FIG. 4 is a schematic block diagram of an exemplary embodiment of themobile office platform engine machine for use in the system of FIG. 1.

FIG. 5 is a schematic block diagram of an exemplary embodiment of thedatabase module of the system of FIG. 1.

FIG. 6 is a schematic block diagram of another embodiment of userinterface components of the direct access proxy similar to that shown inFIG. 2.

FIG. 7 is a block diagram showing a comparison of a logical structurefor a non-localized and a localized/runtime structure as used in someknown systems.

FIG. 8 is a fragmentary hierarchy view of localized templates versusbranded localized templates as used in some known systems.

FIG. 9A is a sequence diagram specifying process flow for calling anextension object to retrieve a localized string.

FIG. 9B is a sequence diagram specifying process flow for calling anextension object to execute an XSLT template.

FIG. 10 is a fragmentary hierarchy view of an HTML proxy havingdifferent XSL files in a hierarchy as illustrated.

FIG. 11 is a block diagram of different components in the system used inthe template rendering (transformation) for transforming applicationdata into presentation information.

FIG. 11A is another block diagram of an example of the components thatcan be used in the template rendering (transformation).

FIG. 12 is a high-level block diagram of a resource deployment packageand showing a descriptor and subsets of French, German and a carrierresource.

FIG. 13 is a high-level block diagram of components that can be involvedin resource deployment and a high-level process flow for resource push.

FIG. 14 is a block diagram showing a deployment service that can be usedin a non-limiting embodiment.

FIG. 15 is a schematic block diagram illustrating an exemplary mobilewireless communications device that can be used with the Direct Accesssystem shown in FIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Different embodiments will now be described more fully hereinafter withreference to the accompanying drawings, in which preferred embodimentsare shown. Many different forms can be set forth and describedembodiments should not be construed as limited to the embodiments setforth herein. Rather, these embodiments are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope to those skilled in the art. Like numbers refer to like elementsthroughout.

A system renders presentation pages. A server includes an extensiblestylesheet transformation (XSLT) module. A storage medium contains atleast one of images and text. The XSLT module is operative for callingan XSL extension and rendering the at least one of images and text intoa presentation page based on a language requirement at a foreign locale.

The presentation page can be rendered into localized content based onlocale. Resource bundles can contain at least one of localized imagesand text and be rendered into an XML document to be processed by theXSLT module to generate localized content, which can be in a foreignlanguage used at the locale.

In another aspect, the XSL extension can be formed as a JAVA extensionand the XSLT module can render HTMP or WAP output. The server could beformed as a web server or email server. The server can also be operativefor storing a plurality of resource deployment packages (RDP's), eachRDP comprising deployment content that can be deployed based on locale.

In yet another aspect, the system can render presentation pages in awireless communications system. A mobile wireless communications deviceis operable for communicating over a wireless communications networkwith a mobile office platform that includes an extensible stylesheettransformation (XSLT) module. A storage medium contains at least one ofimages and text. The XSLT module is operative for calling an XSLextension and rendering the at least one of images and text into apresentation page on the mobile wireless communications device based ona language requirement at a foreign locale.

A method aspect is also set forth.

Referring initially to FIG. 1, a direct access (DA) email distributionand synchronization system 20 allows direct access to different mailsources, allowing messages to be transferred directly to a mobilewireless handheld device from a source mailbox. As a result, differentmail stores need not be used for integrated external source mailaccounts, and a permanent copy of an email in a local email store is notrequired.

Although this diagram depicts objects as functionally separate, suchdepiction is merely for illustrative purposes. It will be apparent tothose skilled in the art that the objects portrayed in this figure canbe arbitrarily combined or divided into separate software, firmware orhardware components. Furthermore, it will also be apparent to thoseskilled in the art that such objects, regardless of how they arecombined or divided, can execute on the same computing device or can bearbitrarily distributed among different computing devices connected byone or more networks.

The direct access system 20 enables email users or subscribers to haveemail from third party email services pushed to various mobile wirelesscommunications devices 25. Users need not create a handheld emailaccount to gain direct access to an existing external email account. Thedirect access system 20 may operate without performing aggregation asused in some prior art systems, in which emails are aggregated frommultiple different source mailboxes to a single target mailbox. In otherwords, email need not be stored in an intermediate target mailbox, butinstead may advantageously be accessed directly from a source mailstore.

As illustrated in FIG. 1, the direct access system 20 illustrativelyincludes a Web client (WC) engine 22 and a mobile office platform (MOP)24. These Web client engine 22 and mobile office platform 24 operatetogether to provide users with direct access to their email from mobilewireless communications devices 25 via one or more wirelesscommunications networks 27, for example. Both the Web client engine 22and the mobile office platform 24 may be located at the same location orat separate locations, and implemented in one or more servers. The webclient engine 22 illustratively includes a port agent 30 forcommunicating with the wireless communications devices 25 via thewireless communications network(s) 27, a worker 32, a supervisor 34, andan attachment server 36, which will be discussed further below. An alertserver 38 is shown in dashed lines, and in one preferred embodiment, isnot used, but could be part of the system in yet other embodiments.

The mobile office platform 24 illustratively includes a DA proxy 40, anda proxy application programming interface (API) 42 and a cache 44cooperating with the DA proxy. The mobile office platform 24 alsoillustratively includes a load balance and cache (LBAC) module 46, anevent server 48, a universal proxy (UP) Servlet 54, an AggCron module56, a mobile office platform (MOP) engine 58, and a database (DB) engine60, which will be discussed in further detail below. The Least RecentlyUsed (LRU) cache 41 caches new messages, and can release messages andobjects that were least recently used.

The supervisor 34 processes new mail notifications that it receives fromthe direct access proxy 40. It then assigns a job, in the form of a UserDatagram Protocol (UDP) packet, to the least-loaded worker 32, accordingto the most recent UDP heartbeat the supervisor 34 has received. Forpurposes of this description, heartbeat is a tool that monitors thestate of the server. Additionally, the supervisor 34 will receive a newservice book request from the direct access proxy 40 to send servicebooks to the mobile wireless communication device for new or changedaccounts. A service book can be a class that could contain all servicerecords currently defined. This class can be used to maintain acollection of information about the device, such as connectioninformation or services, such as an email address of the account.

The worker 32 is an intermediary processing agent between the supervisor34 and the port agent 30, and responsible for most processing in the Webclient engine 22. It will retrieve e-mail from a universal proxy 54, viaa direct access proxy, and format e-mail in Compressed MultipurposeInternet Mail Extension (CMIME) as a type of Multipurpose Internet MailExtension, and send it to the port agent 30, for further processing. Itsresponsibilities include the following tasks: (1) messages sent to andreceived from the handheld; (2) message reply, forward and morerequests; (3) Over The Air Folder Management operation (OTAFM); (4)attachment viewing; and (5) service book.

The port agent 30 acts as a transport layer between the infrastructureand the rest of the Web client engine 22. It is responsible fordelivering packets to and from the mobile wireless communicationsdevice. To support different integrated mailboxes with one device, morethan one service book can be used, and each service book can beassociated with one integrated mailbox. A port agent 30 can include oneServer Relay Protocol (SRP) connection to a relay, but it can alsohandle multiple SRP connections, and each connection may have a uniqueGlobally Unique Identifier (GUID) associated with a service book. Theattachment server 36 provides service for document/attachment conversionrequests from workers 32.

The direct access proxy 40 provides a Web-based Distributed Authoringand Versioning (WebDAV) interface that is used by the worker 32 toaccess account and mailbox information. This provides functionality tocreate, change and move documents on a remote server, e.g., a Webserver. The direct access proxy 40 typically will present anasynchronous interface to its clients. The LBAC module 46 is used by anotification server and the Web client engine 22 components to locatethe proper DA proxy for the handling of a request. The universal proxyServlet 54 abstracts access to disparate mail stores into a commonprotocol. The event server 48 responds to notifications of new messagesfrom corporate servers 52 and/or mail service providers 50, which may bereceived via the Internet 40, for example. The notifications arecommunicated to the direct access proxy 40 by the AggCron module 56 andthe event server 48 so that it may initiate checking for new mail onsource mailboxes 51, 53 of the mail service providers 50 and/orcorporate servers 52. The proxy API can be a Simple Object AccessProtocol (SOAP) Daemon 42 and is the primary interface into a database60, which is the primary data store for the mobile office platform 24.The AggCron module 56 may also periodically initiate polling for newmessages as well.

FIG. 2 is a high-level block diagram showing user interface componentsof the direct access proxy 40. More particularly, the direct accessproxy 40 illustratively includes an identifier module 72 with variousdownstream proxy modules for different communication formats, such as aWireless Application Protocol (WAP) proxy module 74 and a HypertextMarkup Language (HTML) proxy module 76. Of course, it will beappreciated by those skilled in the art that other types of proxymodules for other communications formats may also be used.

The identifier module 72 provides a centralized authentication servicefor the direct access system 20 and other services. An authenticationhandshake may be provided between an ID service and direct access system20 to ensure that users have the proper credentials before they areallowed access to the direct access system 20. The ability to switchfrom managing a Web client to a direct access system, or vice versa, mayoccur without requiring the user to re-enter any login credentials. AnyWeb client and direct access may share session management information onbehalf of a user.

The WAP proxy 74 provides a wireless markup language (WML)-based userinterface for configuring source mailboxes with the mobile officeplatform 24. The HTML proxy 76 provides an HTML-based user interface forconfiguring of source mailboxes in the MOP 24. The proxy API 42 (SOAPDaemon) is the primary interface into the database 60. The engine 58 isa protocol translator that connects to a source mailbox to validateconfiguration parameters. The database 60 is the primary user data storefor the mobile office platform 24.

FIGS. 3, 4 and 5 illustrate respective Web client engine machines 80(FIG. 3), an engine machine 82 (FIG. 4), and database machine 84 (FIG.5). The Web client engine machine 80 illustratively includes thesupervisors 34, workers 36, and port agents 38. Relays 86 cooperate withthe port agents 38 using a GUID.

The engine machine 82 illustratively includes a direct access proxy 40,HTML proxy 76, WAP proxy 74, PDS module 88, UP Servlet 54, LBAC module46, a sendmail module 90, an secure mail client (SMC) server 92, asecure sockets layer (SSL) proxy 94, an aggregation engine 96, and eventserver 48. The SMC server 92 cooperates with corresponding SMC modulesresident on certain corporate networks, for example, to convey emaildata between the mobile office platform 24 and source mailboxes. Thedatabase machine 84 may include an aggregation application programminginterface (API) 100 as a SOAP Daemon, an administration console 102, anaggregation database 104, the AggCron module 56, an SMC directory server106, and a send mail module 90.

The various components of the Web client engine 22 may be configured torun on different machines or servers. The component binaries andconfiguration files may either be placed in a directory on the networkor placed on a local disk that can be accessed to allow the appropriatecomponents to run from each machine. In accordance with one exemplaryimplementation, deployment may include one supervisor, two workers, andone port agent for supporting 30,000 external source mailboxes, althoughother configurations may also be used. Actual production deployment maydepend on the results of load, performance and stress testing, as willbe appreciated by those skilled in the art.

For the mobile office platform 24 direct access components, modules andvarious functions, machines are typically installed in twoconfigurations, namely engine machines (FIG. 4) and database machines(FIG. 5). While these machines may have all of the above-describedcomponents installed on them, not all of these components need be activein all applications (e.g., aggregation may be used with systems that donot support push technology, etc.). Once again, actual productiondeployment may depend on the results of load, performance and stresstesting.

The mobile office platform 24 architecture in one known techniqueadvantageously uses a set of device/language-specific eXtensibleStylesheet Language (XSL) files, which transform application data intopresentation information. In one non-limiting example, a build processtakes a non-localized XSL and generates a localized XSL for eachsupported language. When the XSL is used, it is “compiled” in memory andcached for repeated use. The purpose of pre-localizing and caching thetemplates is to reduce the CPU cycles required to generate apresentation page.

Branding may also be performed. Initially, a localized XSL may build aWAP application to access aggregated email accounts. A WAP proxyapplication may be localizable and support multiple WAP devices. Foreach logical page of an application, a device-specific XSL may becreated, which may be localized for each language/country supported.This rendering scheme may support not only WAP devices, but also SMTP,HTML and POP proxies, for example. In branding, each page of a givenapplication may be customized for each different brand.

The branding of a page may be accomplished through XSL imports,including the use of a Java application programming interface (API) forXML processing (JAXP) feature to resolve the imports dynamically. Thisneed not require that each combined page/brand template be compiled andcached. By way of example, in a sample template directory, first andsecond pages for a single language/country may be combined with brandedcounterparts to generate a plurality of distinct template combinations.It is also possible to profile memory requirements of an application byloading templates for a single language, device/application and brand.An HTML device may include a set of templates that are large compared toother devices.

In one known technique, the mobile office platform 24 advantageouslybuilds processes and takes non-localized files and language-specificproperty files and combines them to make each non-localized XSL into anXSL for each supported language. A separate XSL for each language neednot be used, and the language factor may be removed from the memoryusage equation. A JAXP API may be used to extend XSL with Java classes.The extensions may take various forms, for example, including extensionelements and extension functions. A template may be transformed bycreating and initializing an extension object with a locale and passingan object to a transformer. The system can remove multiple imports anduse less memory. HTML templates can use template importing to enabletemplate reuse, much like Java classes, and reuse other Java classesthrough a mechanism like derivation or importing.

In the direct access system 20, users receive email on their mobilewireless communications devices 25 from multiple external accounts, andwhen replying to a received message, the reply-to and sent-from addressintegrity is preserved. For example, for a user that has an integratedYahoo! account (user@yahoo.com) and a POP3 account (user@pop3.com), ifthey receive an email at user@yahoo.com, their replies generated fromthe device 25 will appear to come from user@yahoo.com. Similarly, if auser receives an email at user@pop3.com, their replies will appear tocome from user@pop3.com.

Selection of the “sent from” address is also available to a user thatcomposes new messages. The user will have the ability to select the“sent from” address when composing a new message. Depending on thesource mailbox type and protocol, the message may also be sent throughthe source mail service. This functionality can be supported by sendinga configuration for each source mailbox, for example, as a non-limitingexample, a service book for each source mailbox 51, 53 to the mobilewireless communications device 25.

As noted above, a service book is a class that may include all servicerecords currently defined. This class may be used to maintain acollection of information about the device, such as connectioninformation. The service book may be used to manage HTTP connections andmail (CMIME) information such as account and hierarchy. At mobilewireless communications devices 25, a delete service book request may besent when a source mailbox 51, 53 is removed from the account. Theservice book may also be resent to the device 25 with a viewable namethat gives the user some indication that the selection is no longervalid.

A sent items folder may also be “synchronized.” Any device-originatedsent messages may be propagated to a source account and stored in a sentmail folder, for example. Also, messages deleted on the device 25 maycorrespondingly be deleted from the source mailbox 51, 53. Anotherexample is that device-originated marking of a message as read or unreadon the device 25 may similarly be propagated to the source mailbox 51,53. While the foregoing features are described as source-dependent andsynchronizing one-way, in some embodiments certain synchronizationfeatures may in addition, or instead, propagate from the sourcemailbox/account to the handheld device, as will be appreciated by thoseskilled in the art.

When available, the mail service provider or corporate mail server maybe used for submission of outgoing messages. While this may not bepossible for all mail service providers or servers, it is preferrablyused when available as it may provide several advantages. For example,subscribers to AOL will get the benefit of AOL-specific features likeparental controls. Furthermore, AOL and Yahoo users, as non-limitingexamples, will see messages in their sent items folder, and messagesrouted in this manner may be more compliant with new spam policies suchas Sender Policy Framework (SPF) and Sender Id. In addition, messagessent via corporate mail servers 52 will have proper name resolution bothat the global address list level and the personal level. It should beunderstood, however, that the use of the mail service provider 50 todeliver mail may be dependant on partner agreements and/or protocol,depending upon the given implementation.

The architecture described above also advantageously allows for featuressuch as on-demand retrieval of message bodies and attachments andmultiple folder support. Moreover, a “this-is-spam” button or indicatormay be used allowing company labels and other service provider-specificfeatures when supported by an underlying protocol, as will beappreciated by those skilled in the art.

One particular advantage of the direct access system 20 is that a userneed not configure an account before integrating additional accounts.However, a standalone email address may be used, and this addressadvantageously need not be tied to a mailbox size which the subscriberis required to manage. For example, the email account may be managed byan administrator, and any mail could be purged from the system after apre-determined period of time (i.e., time-based auto-aging with nomailbox limit for all users).

Additionally, all aspects of any integrated email account creation,settings and options may advantageously be available to the user fromtheir mobile wireless communications device 25. Thus, users need notvisit an HTML site and change a setting, create a filter, or performsimilar functions, for example. Of course, an HTML site may optionallybe used.

As a system Internet email service with the direct access system 20grows, ongoing emphasis may advantageously be placed on theadministrative site to provide additional information to carrieradministrators, support teams, and similar functions. However, in someinstances a mail connector may be installed on a personal computer, andthis functionality may not always be available from the mobile wirelesscommunications device.

The Web client engine 22 may advantageously support different featuresincluding message to handheld (MTH), message from handheld (MFH),forward/reply a message, request to view more for a large message (e.g.,larger than 2K), request viewing message attachment, and over the airfolder management (OTAFM). These functions are explained below.

For an MTH function, each email account integrated for a user is linkedwith the user device through a Web client service book. For each newmessage that arrives in the Web client user mailbox, a notification thatcontains the new message information will typically be sent to a Webclient engine supervisor component (FIG. 3), which in turn will assignthe job to an available worker with the least load in the system. Thechosen worker 32 will validate the user information and retrieve the newmessage from the user source mailbox and deliver it to the user device.

In an MFH function, MFH messages associated with a Web client servicebook are processed by the Web client engine 22 and delivered to theInternet 49 by the worker 32 via the simple mail transfer protocol(SMTP) or native outbox. If a user turns on the option to save the sentmessage to the sent items folder, the direct access proxy will save acopy of the sent message to this folder.

In a Forward/Reply/More function, the user can forward or reply an MTHor MFH message from the mobile wireless communications device 25 as longas the original message still existed in the direct access proxy cacheor in user mailbox. For MTH, the worker 32 may send the first 2K, forexample, or the whole message (whatever is less) to the user device. Ifthe message is larger than 2K, the user can request MORE to view thenext 2K of the message. In this case, the worker 32 will process theMore request by retrieving the original message from the user sourcemailbox, and send back the 2K that the device requests. Of course, insome embodiments more than 2K of message text (or the entire message)may be sent.

In an attachment-viewing function, a user can view a message attachmentof a popular document format (e.g., MS Word, MS Power Point, MS Excel,Word Perfect, PDF, text, etc.) or image format (GIF, JPEG, etc). Uponreceiving the attachment-viewing request, which is implemented in a formof the more request in this example, the worker 32 can fetch theoriginal message from the user source mailbox via the direct accessproxy, extract the requested attachment, process it and send result backto the user device. The processing requires that the original messagehas not been deleted from the user Web client mailbox.

In the save sent message to sent items folder function, if the userturns this option on, the worker 32 places a copy of each MFH messagesent from the user device in the user sent items folder in the mailbox.In over the air folder management, the Web client OTAFM servicemaintains any messages and folders in the user mailbox synchronized withthe user device over the air.

Whenever a message in the user source mailbox is Moved/Deleted, theassociated message on the device may also be Moved/Deleted accordingly,and vice-versa. When a message is Moved/Deleted on the device, theassociated message in the user Web client mailbox may also beMoved/Deleted accordingly. Similarly, when a folder isAdded/Removed/Renamed from the user Web client mailbox, the associatedfolder on the device may be Added/Removed/Renamed, and vice-versa.

The system 20 may advantageously support different subsets of variousmessaging features. For example, in the message to handheld function,the mobile office platform 24 may be responsible for connecting to thevarious source mailboxes 51, 53 to detect new emails. For each new mail,a notification is sent to the Web client engine 22 and, based on thisnotification, the supervisor 34 chooses one of the workers 32 to processthat email. The chosen worker will fetch additional account informationand the contents of the mail message from the direct access proxy 40 anddeliver it to the user device 25.

In a message sent from handheld function, the MFH could be given to thedirect access proxy 40 from the Web client worker 32. In turn, themobile office platform 24 delivers a message to the Internet 49 bysending through a native outbox or sending it via SMTP. It should beunderstood, however, that the native outbox, whenever possible, mayprovide a better user experience, especially when taking into accountcurrent anti-spam initiatives such as SPF and sender Id.

In a message deleted from handheld function, when a message is deletedfrom the device 25, the Web client engine 22 notifies the mobile officeplatform 24 via the direct access proxy 40. As such, the mobile officeplatform 24 can delete the same message on the source mailbox.

When handling More/Forward/Reply/Attachment viewing requests, the Webclient worker 32 may request an original mail from the direct accessproxy 40. It will then process the request and send the results to themobile wireless communications device 25. The architecture mayadditionally support on-demand retrieval of message parts and otherupgrades, for example.

Upon the integration of a new source mailbox 51, 53, the service booknotification from the alert server 38 may be sent to the supervisor 34,which assigns this notification to a worker 32 for sending out a servicerecord to the device. Each source mailbox 51, 53 may be associated witha unique service record. In this way, each MFH message is linked with asource mailbox 51, 53 based on the service record on the device.

The system 20 may also poll the integrated external mailboxesperiodically to check for new mail and to access any messages. Thesystem 20 may further incorporate optimizations for polling bandwidthfrom an aggregation component allowing a quick poll. The system 20 canalso advantageously support a large active user base and incorporate arapidly growing user base.

The topology of load balancing can be based on the size of a component'squeue and its throughput. These load statistics can be monitored by amechanism in one example called the UDP Heartbeat, as described before.If a component is overloaded or has a large queue size, the componentwill have less chance to get an assigned job from other components. Incontrast, a component will get more assigned jobs if it completes morejobs in the last few hours than other components. With this mechanism,the load could distribute over heterogeneous machine hardware, i.e.,components running on less power machines will be assigned fewer jobsthan those on machines with more power hardware.

General load balancing for any mobile office platform components can beaccomplished through the use of a load balancer module, for example, aBIG-IP module produced by F5 Networks of Seattle, Wash. BIG-IP canprovide load balancing and intelligent layer 7 switching, and can handletraffic routing from the Internet to any customer interfacing componentssuch as the WAP and HTML proxies. The use of a BIG-IP or similar modulemay provide the application with pooling capabilities, fault toleranceand session management, as will be appreciated by those skilled in theart.

Typically, access to a single source mailbox 51, 53 can be from a singledirect access proxy 40 over a persistent connection. Any requests onbehalf of a particular user could persist to the same machine in thesame direct access clustered partition. As certain components aresystem-wide and will be handling work for users across many partitions,these components can be designed to determine which direct accesspartition to communicate with on a request-by-request basis.

The load balancer and cache (LBAC) 46 may support this function. TheLBAC 46 is a system-wide component that can perform two importantfunctions. The first of these function is that it provides a mappingfrom the device PIN to a particular direct access proxy 40, whilecaching the information in memory for both fast access and to save loadon the central database. Secondly, as the direct access proxy 40 will berun in clustered partitions, the LBAC 46 may distribute the load acrossall direct access proxies within any partition.

The LBAC 46 can be formed of different components. For example, the codewhich performs the load balancing can be an extended version of a securemail connector. The code can also perform lookups to the centraldatabase and cache the results (LBAC).

In one non-limiting example, when a worker requires that a direct accessproxy 40 perform work, it provides the LBAC 46 with a device PIN. TheLBAC 46 will discover which partition that PIN is associated with bylooking in its cache, or retrieving the partition identifier from acentral database (and caching the result). Once the partition is known,the LBAC 46 then consults its cache to see which direct access proxy inthat partition has been designated to handle requests for that PIN. Ifno mapping exists, the LBAC requests the PDS to create a new associationon the least loaded DA proxy 40 (again caching the result). Finally, theLBAC 46 responds to the worker 32 with the connection information forthe proper direct access proxy to handle that particular request.

The secure mail connector 88 may run in failover pairs, where one is anactive master and the other is a secondary standby. Internal datastructures may be replicated in real-time from the master to thestandby. Multiple LBACs 46 can be run for scalability and faulttolerance, but typically would require an external connection balancingcomponent, such as the BIG-IP component as explained before.

A receiving component in the Web client engine 22 saves the job that hasbeen assigned to it from other components to a job store on the diskbefore processing. It can update the status of the job and remove thejob from the job store when the job processing is completed. In case ofcomponent failure or if the process is restarted, it can recover thejobs from the job store and, based on the current statuses of thesejobs, continue processing these jobs to the next state, saving the timeto reprocess them from the beginning.

Any recovery from the standpoint of MTH/MFH can be achieved throughcurrent polling behavior and on the Web client engine 22 recoverymechanisms. From within the mail office platform components, until amessage has been successfully delivered to a Web client engine 22, thatmessage is not recorded in the partition database 60. During the nextpolling interval, the system can again “discover” the message andattempt to notify the Web client engine 22. For new mail events, if anevent is lost, the system can pick up that message upon receiving thenext event or during the next polling interval. For sources supportingnotifications, this interval could be set at six hours, as onenon-limiting example. For messages sent from the Web client engine 22,and for messages that have been accepted by the Web client engine,recovery can be handled by different Web client engine components.

The Web client engine 22 may advantageously be horizontally andvertically scalable. Multiple supervisors 34 can beregistered/configured with direct access proxies 40 to provide thedistribution of the notification load and the availability of engineservice. Multiple workers 32 and port agents 30 can run on the samemachine or across multiple machines to distribute load and achieveredundancy. As the number of users grows, new components can be added tothe system to achieve high horizontal scalability.

It is possible for a new component to be added/removed to/from thesystem automatically without down time. Traffic can automatically bedelegated to a new component and diverted away from failed components.Each component within the mobile office platform 24 can be deployedmultiple times to achieve horizontal scalability. To achieve verticalscalability, each mobile office platform 24 component can be amulti-threaded process with a configurable number of threads to scaleunder heavy load. Pools of connections can be used to reduce theoverhead of maintaining too many open connections.

FIG. 6 is another embodiment of the high level architectural diagram ofthe BDA user interface components similar to the functional componentsshown in the diagram of FIG. 2. There will now follow a briefdescription of these basic components and their function.

Provisioning (PRV) 110 provides a centralized database 111 or store toaccess user and device Identifier (ID) profile information. Duringlogin, the WAP and HTML Proxies 74, 76 retrieve the ID profile, whichprovides user and device information. Proxies update PRV 110 for certainuser configuration actions, such as a changed PIN. The web clientdatabase 112 (WC DB) contains account information for web client users.It is queried during login to determine if an unknown user is a webclient user and whether they can be migrated. The WAP Proxy 74 providesa Wireless Markup Language (WML) based user interface for configurationof source mailboxes in the Mobile Office Platform (MOP). The HTML Proxy74 provides an HTML based user interface for configuration of sourcemailboxes in MOP. The Soap Servlet 114 (SOAP Daemon) provides aninterface into a database store. The Agg Engine 116 acts as a protocoltranslator that connects to a source mailbox to validate configurationparameters. The Mobile Office Platform Database (MOP DB) 118 is aprimary user data store for the MOP. The Web Admin provides the MOP withnotifications of account state changes. Provisioning 110 also providesnotification of account state changes, such as inactive and active.Provisioning (PRV) can be used to notify and migrate a user from a WebClient (WC) service to an Internet Service (IS), having more advancefeatures that are accessible from a web browser with a user emailaccount, allowing a user to add and edit email accounts.

The Web Client Aggregation Programming Interface (WC AggAPI) 122includes a database 124 and provides integrated source data for WCaccounts. It is queried to retrieve integrated source configuration datato be migrated to a new Internet Service (IS) account for the user. TheWC DB 112 provides web client account information. It is queried toretrieve web client account configuration data to be migrated to aInternet Service account for the user. The system can make use ofexisting products such as the Provisioning 110 and WebAdmin 120. Theseproducts have scaling characteristics. In this described embodiment,functionality has moved from Aggcron to the BDA proxy. The systemprovides a direct connection to a partition database within the BDAproxy. Access to the database can be from a configurable connection poolthat will grow and shrink as necessary, depending on the needs of thesystem. The pool can recover from network errors and databaseconnectivity issues.

The DA System 10 is operative to allow a set of device/language specificXSL files to transform application data into presentation information. Abuild process takes a non-localized XSL and generates a localized XSLfor each language supported by the product as shown in FIG. 7. Asillustrated, a logical pattern of three pages 200 is shown. Anon-localized system 202 is shown with individual templates anddifferent pages 1-3 in respective device 1 and device 2. A localizedruntime system 204 is shown with devices, languages countries and pages.At runtime, when the XSL is used it is “compiled” in memory and cachedfor repeated use. The purpose of pre-localizing and caching thetemplates is to minimize the CPU cycles required to generate apresentation page.

The localized XSL scheme can build a WAP application to accessaggregated email accounts, a.k.a. a WAP proxy, which can be localizable,but also support multiple WAP devices. For each logical page of theapplication, a device specific XSL can be created, which would belocalized for each language/country supported.

The rendering scheme does not have to support WAP devices, and an HTMLand POP Proxy can be used. Furthermore, there are other applicationsdefined for particular devices (e.g., Admin application for HTML).Branding is possible where each page of any given application can becustomized for each different brand as shown in FIG. 8. As illustrated,localize templates 210 are shown and can be compared to the illustratedbranded localized templates 212. The branding of a page can be done atruntime through XSL imports, using a JAXP feature to resolve the importsdynamically. This method does require that each combined page/brandtemplate be compiled and cached.

In the sample template directory shown above in FIG. 8, Page 1 and Page2 for a single language/country would be combined with its brandedcounterparts to generate four distinct template combinations, asfollows:

-   -   a) Device1/lang1/entry1/Page1/Brand1;    -   b) Device1/lang1/entry1/Page1/Brand2;    -   c) Device1/lang1/entry1/Page2/Brand1;    -   d) Device1/lang1/entry1/Page2/Brand1;

The DA System 10 supports five languages and some 20+ brands in onenonlimiting example, and the MOP 14. Any new devices/applications (e.g.,HTML), localization and branding requirements would demand extra memoryto cache pre-localized and branded templates. This is a large factor inthe scaling of the proxies.

The memory requirements of an application can be profiled by loading allthe templates for a single language, device/application and brand. AnHTML device can be used because it contains a set of templates that arelarge, compared to other devices.

One example of a profiler for use the system 10 is the Jfluid profileroperative with a NetBeans environment, which allows a comparison ofmemory usage to known and new systems. An application can read a proxyservlet action map to retrieve the location of templates used in theHTML Proxy. Xalan libraries can be loaded into memory by loading atemplate and a transformation can be performed. The profiler's resultscan be reset. The templates can be loaded and the profiler stopped. Onenon-limiting example of results are as follows:

-   -   1) 121 principal templates;    -   2) 44371672 bytes or about 42.3 megabytes;    -   3) 358 kilobytes per template;        In this example:    -   1) 147 unique templates were loaded (121 principal 26 imported);    -   2) 719 templates were loaded; and    -   3) A main.xsl was loaded 177 times.        The main.xsl file will be explained in detail below.

In this example, the following steps were performed:

-   -   1) Loaded/compiled a template;    -   2) Performed a transform;    -   3) Started a timer; and    -   4) Performed 1000 transformations of an XML document with the        loaded template.

The template was of average size and contained 35 localized strings. Themachine was a desktop box (2.8 ghz 500 mg). The results were 19.2 ms pertransformation.

If the results for the HTML proxy were extrapolated into support of fivelanguages and twenty brands, an HTML proxy running under a DA system 10would require in this nonlimiting example, 20 brands*5 languages*42.3megabytes=4.13 gigabytes.

The address space of a 32 bit processor may not accommodate the memoryrequirements. Furthermore, such memory requirements are not practicaland could degrade the performance on the machines having the proxies.Adding more brands or languages could make those memory requirementsgrow steadily.

To reduce the memory requirements, the system could make the variablesthat calculate memory usage constant. The number of brands and/orlanguages used as a multiplying factor in calculating memory usage couldbe reduced.

Because template creation and caching can be designed in a way optimalfor CPU usage, any reductions in memory usage could make the proxyfaster, even though transformation times may increase. The descriptionwill proceed relative to XSLT as the rendering scheme, although othersoftware programs known to those skilled in the art could be used.

A build process could take non-localized XSL's and language specificproperty files and combine them to make each non-localized XSL into anXSL for each supported language. A separate XSL for each language ispossible and the language factor can be removed from the memory usageequation. In one example of the DA system 10, the HTML proxy wouldrequire about 20 brands*1 language-neutral*42.3 megabytes=846 megabytes.Adding a language typically should only require some constant memoryincrease depending on the language, and it would no longer be amultiplier. Thus, there can be runtime localization even though there issome variation.

Java applications typically use ResourceBundles to store languagesensitive strings that will be viewed by a user. Any class file thatrequires a language sensitive string typically can load a ResourceBundleand retrieve it with a pre-defined ID. The data for a ResourceBundlecould be contained within a property file or Java code. For propertyfiles a standard naming convention could be used for determining whichproperty file to load for a particular language/locale. Some propertyfiles could be organized in a “resource” directory in subdirectories foreach language, e.g., English(En) or French (Fr) as non-limitingexamples. In each of those language directories there may be countrysubdirectories, e.g., US, UK. Each property file could be moved out ofthe language and country subdirectories and renamed such as:

-   -   Filename[_language[language[_country].property.        An example could be:

Resource\fr\mainmenu.xsl -> Resource\mainmenu_fr.xslResource\en\uk\mainmenu.xsl -> Resource\mainmenu_en_uk.xsl

XSL's could also obtain transform data from an XML document, but itcould be prohibitive to retrieve all strings in all property files for agiven language and convert them to XML, thus allowing the XSL to querythe few strings that it requires. The (JAXP) can provide a mechanism forextending XSL with Java classes. It can support processing of XMLdocuments using DOM, SAX, and XSLT. It enables applications to parse andparticular XML processing implementation. The extensions can take twoforms, 1) extension elements and 2) extension functions, such as Apacheextensions. For purposes of the following description, extensionfunctions will be explained.

When a template is to be transformed, an extension object instance canbe created and initialized with a locale. This object is passed to atransformer. The XSL declares the extension function class and uses avalue-of element to execute the function, passing it the extensionobject instance passed to it in the parameter.

A renderer, typically formed as a processor, could obtain the packagewhere the ResourceBundles are stored. This can either be stored in aservlet configuration or hardcoded into code, such as:

-   -   ResourceBundlePackage=“com.teamon.resource”

An extension function provides template access to ResourceBundles, suchas:

Public ResLoader  public ResLoader(Locale locale, String resPackage)   m_locale=locale;   public getString(String inbundle, String name)   bundle=resPackage+bundle;   ResourceBundle bundle=ResourceBundle.getBundle (m_locale,bundle);   bundle.getString(name);

The renderer could make the extension object instance available asparameter, such as:

ResLoader res=new Resloader(locale); params.put(“ResLoader”,res);transform.setParameters(params); transform.process( );

An XSL file could define and use the extension object instance to load astring such as:

<Xsl:transform> attributes:   xmlns:xalan=http://xml.apache.org/xalan  xmlns:res=“xalan://com.teamon.util.xml.ResLoader”  extension-element-prefixes=“res” ResLoader Param:   <xsl:paramname=”ResLoader”/> localizing strings:   <xsl:value-of  select(‘res:getValue($ResLoader,”bundle”,”stringID”))/>

Naming the ResourceBundle in a getValue call may not match how templatescurrently specify where to find the resource strings. A differentapproach that mirrors that model could be to provide a loadResourceextension function. The extension object could track which resourceshave been loaded and when a getValue( ) is called find the string in oneof the loaded resources.

<xsl:value-of select(‘res:LoadResource($ResLoader,”foo”))/>

It is possible to use Thread Local Storage (TLS) instead of a parameterto store the extension object instance to simplify the value-ofstatement. This could be used in conjunction with variation a and avalue-of statement could be:

-   -   <xsl:value-of select(‘res:getValue(“stringID”))/>

An extension element used in conjunction with a TLS variation and theXSL could become more readable such as:

<res:getValue bundle=”foo” name=”stringID”/> or <res:loadResourcename=”foo”/> <res:getValue name=”stringID”/>

The system could organize the ResourceBundles in multiple packages.Anywhere the bundle is passed as an argument/attribute, the entirepackage can also be passed:

  <xsl:value-of select(‘res:getValue($ResLoader,“com.attachmate.resource.foo”,stringID”))/>

A template as described could be modified using the variation asdescribed, on a similar test as applied and a difference measured as a19.4 ms average transformation. This is an increase of approximately 0.2ms. Because there are 35 localized strings in this template, a perstring overhead of approximately 0.005 ms average string load time canbe inferred.

A profiler can be used to measure the time percentage spent loading theresource string. The results showed are 2.2% of the template transformtime was spent loading the 35 strings. Any discrepancy could be theresult of having only 50 transformations performed during profiling,rather than 1000 as a test application accomplishes.

As a result, the added overhead of calling an extension function doesnot overextend CPU usage and decreases memory usage.

In one non-limiting example, the process for migrating code andtemplates to a new system from a previously known system could includethe following steps:

-   -   1. Move property files to source directory (e.g.        com.teamon.resource) and change names to conform to        ResourceBundle standards;    -   2. Add resource package directory configuration;    -   3. Create Extension function class;    -   4. Modify Renderer to create extension object instance and make        available to template;    -   5. Modify caching scheme to cache based on template and brand        and not language;    -   6. Create Migration utility for existing templates;    -   7. Replaces $xxx variables with the appropriate xsl element(s);        and    -   8. If migration utility is not the localizer, the system removes        the localizer from build.

FIGS. 9A and 9B are non-limiting examples setting forth process flow.FIG. 9A shows the process flow for calling the extension object toretrieve a localized string. FIG. 9B shows the process flow for callingan extension object to execute an XSLT template.

Within a principal template's import chain, some templates could beimported multiple times. Removing the multiple imports would typicallyuse less memory. For example, in the HTML proxy there could be a XSLnamed contact.xsl, which could have the import structure depicted as inFIG. 10. As illustrated, contact 300 includes contact detail 302, phonenumbers 304, business 306, personal 308, corepage 310, main 312 andproperties 314. Two other files could include main.xsl andproperties.xsl 314. Both main.xsl 312 and properties.xsl 314 could beimported a number of times, (for example, six) for the contact.xsltemplate in this example. The size of main and properties isapproximately 110 k in this nonlimiting example. This template usesapproximately 550 k (5×110) more memory than is actually required.

From the test application statistics noted above, it can be shown thattwo templates, main.xsl and properties.xsl, were both loaded 177 times,88 of which were redundant. Profiling the memory usages of thesetemplates showed that each instance required:

-   -   1) Main.xsl: 108 k*88=9.55 mb; and    -   2) Properties.xsl: 2.3 k*88=0.2 mb

Removing the redundancies from each template of the HTML proxy couldreduce the memory requirements of this example brand by about 9.75megabytes. If the same savings can be had for all brands, and the DAsystem 10 applies runtime localization, the memory requirements for theHTML proxy in the DA system is:

20 brands*1 lang-neutral*(42.3−9.75)megabytes=651 megabytes.

In this example, the principal template could import main.xsl. To ensureat runtime that redundancy does not occur, the template resolver canprevent multiple imports of branded templates by tracking whichtemplates have been imported. If the template determines that a templateis imported, it can return an empty imported template.

In the DA system 10, templates can be modified so only principletemplates import main.xsl. The TemplateResolver can be modified tofilter out redundant imports.

Because memory use could be extensive, the DA system 10 does not have tocache permanently every template, and caching does not have to occur inall events. This could increase transformation times by approximatelyone order of magnitude (19.2 ms to about 200 ms).

A smart cache could be operative with the system and could work inconjunction with a garbage collector program of the type known to thoseskilled in the art, which typically clears out objects that are takingup space in memory but are no longer in use by a program. One possiblemechanism is to use weak references, but the system possibly would notdecide which reference is to be released. It is possible however, tocreate a proxy work reference.

The Least Recently Used (LRU) cache 41 typically will release objectsthat were least recently used. A smart cache could use multiple factors:

-   -   3) Least Recently used;    -   4) How many times used;    -   5) How much memory it uses; and    -   6) How expensive it is to recreate.

The HTML templates could use template importing processes to enabletemplate reuse, much like a Java Class reuses other Java classes througha mechanism like derivation or importing. The pages of the HTML proxycould be factored into its common pieces to enable reuse. Thisfacilitates creation and maintenance of the HTML user interface. Thememory usage however, is not the same as reusable Java classes, and eachprincipal template has its own classloader and loads its own copy of areused template into memory. Many copies of the same template could becached in memory at the same time. For example, the template main.xslcould be imported by 88 principal templates, and therefore, at least 88copies of it may exist in memory at the same time.

By using a single in-memory copy of non-principal templates, thissignificantly reduces memory usage within a brand. It may also reducememory usage within a brand depending on the amount of common templates.

Table I analyzes memory usage when each template is loaded in memory asingle time. Using the HTML proxy and an example brand, a profiler wasused to determine the memory size of templates that are loaded more thanonce. It was then possible to calculate the memory savings. Table Icontains examples of the templates loaded more than once and the memorydata associated with it.

TABLE I Load Size Total Stylesheet count (bytes) (count*size)brand:\\main.xsl 177 112760 19958520 brand:\\properties.xsl 177corepage.xsl 71 196416 13945536 contents.xsl 71brand:\\helptemplates.xsl 31 191272 5929432 wizard\mainshell.xsl 2532552 813800 Brand:\\pwptemplates.xsl 7 6824 47768addressbookfolder\phone_numbers.xsl 4 55696 222784addressbookfolder\personal.xsl 4 addressbookfolder\business.xsl 4settingsoptions.xsl 4 addressbookfolder\corpcontact_footer.xsl 3 2460073800 addressbookfolder\contact_footer.xsl 3addressbookfolder\contactlist.xsl 2 199600 399200addressbookfolder\contact_detail.xsl 2 format_utils.xsl 2addressbookfolder\corpcontactlist.xsl 2 Totals 819720 41390840 0.8 mb40.4 mb

From an analysis of Table I, it is evident that the memory usage acrossredundantly loaded templates is about 40.4 mb. If each of thosetemplates were only loaded once, it requires about 8 megabytes (mb),saving approximately 39.6 mb. It is thus possible to recalculate thememory usage requirements in a DA system 10 as:

20 brands*1 lang-neutral*(42.3−39.6)megabytes=54 megabytes.

The memory usage will be less if there is any template sharing acrossbrands.

The DA System 10 can have a single instance of a template in memory, butthe standard xsl:import or xsl:include elements preferably should not beused because the templates to be reusable are like Java classes. It isalso possible to use Xalan-Java Extensions. An Xalan-Java Extensionselement allows a template to call a Java method with the transformationcontext and return content. From within the Java method, other templatescan be called, passing along the transformation context, and return thetransformation result as the extensions result. By doing this eachstylesheet is never imported as part of another template. Rather, it iscached separately and can be reused by all templates that require it.

Using the extension element to call templates may limit the ways inwhich templates may be used. For instance, non-principal templatescannot make use of <xsl:apply-templates>. This may result in slightlyless succinct, manageable, reusable code. As an example <xsl:templatematch=“text( )”>, could match all text nodes within an element. Thematch could be more complicated than text( ). A system can use Xpathqueries to make complex matching less complicated. An Xpath query suchas <xsl:apply-templates select=“pd:provider/[@protocol=‘pop’]”> is moreintuitive than having the template itself use <xsl:if> to accomplish thesame task. Xsl:apply-templates may not require the system to haveknowledge of the exact structure of an XML document. It is more flexiblethan, for example, <xsl:for-each> and more resilient to changes in thesource XML structure. This may not be a significant problem in the MOPbecause the input XML is typically known.

<Xsl:import> provides inheritance loading of templates. If there is morethan one imported stylesheet, the one that is imported first has a lowerimport precedence than the one that is imported second, which has lowerimport precedence than the third, and so on. Also, the<xsl:apply-imports> element is used to apply any definitions andtemplate rules of the imported stylesheet has been overridden by theimporting stylesheet. The existing stylesheets do not use thisfunctionality because there are no occurrences of <xsl:apply-imports>.The XSLT 1.0 standard would define extension elements, but it may notdefine an implementation, which could vary. For an XSL stylesheet to beportable across implementations, it must appropriately check for theavailability of an extension element before assuming that it can beused. If the extension element is unavailable, it must provide afallback mechanism. Because the desired template caching behavior cannotbe implemented in pure XSL, we become somewhat tied to Xalan as thesystem's XSLT processor. This should not be a significant limitationbecause the two main Java XSLT processors, Xalan and Saxon, both aresimilar in their implementation and most other processors are likely touse something similar. Hence, switching XSLT processors might not be asignificant time sink.

There are different models that can reuse a template via an extensionelement. There could be separate transforms in which the DOM (DocumentObject Model) is passed to the processor and, a new transformer andoutput stream is created. A DOM is a system in which a document isviewed as a collection of objects which can be individually referenced,thereby allowing for the manipulation of the presentation of thedocument, for example, by the use of Java Script or some other languagein the case of a Dynamic HTML document. Dynamic HTML is similar. Theresult of the transform is returned as the result of the extensionfunction. This model would typically use standard JAXP interfaces, andother templates within the XSL can be called or applied (e.g. match).Some detriment could me an intermediate result buffer and extra buffercopies, a no call-template without modifying template with rootdispatcher, and no parameter passing.

In a single transformer model, the called template element is passed tothe calling templates transformer and executed within its context. Theresult of the transformer is written directly to the caller's outputstream. This model has no intermediate result buffer, and supportsparameter passing. Some detriments could be that it uses non-JAXP Xalaninterfaces, other templates within the XSL cannot be called directly,and each template should be written like a self-contained method.

XSL stylesheets typically do not use the standard <xsl:import> or<xsl:include> top-level elements, given the implementation of anextension element. They could be replaced with an extension element,which could be implemented by a helper object that is responsible forproviding a “call-template” method and a “resource-string” method asexplained above. An example of extension object pseudo-code is shownbelow.

public class XSLTExtension {  public voidcall-template(XSLProcessorContext context, ElemExtensionCall extElem)  {  String href = extElem.getAttribute(“href”);   String name =extElem.getAttribute(“name”);   Templates stylesheet =getStylesheetCache( ).getStylesheet(href);   ElemTemplate template =stylesheet.getTemplateComposed( );   TransformerImpl curtrans =(TransformerImpl)context.getTransformer( );   execute(curtrans,template, extElem);  }  public Stringresource-string(XSLProcessorContext context, ElemExtensionCall extElem) {   String bundle = extElem.getAttribute(“bundle”);   String resKey =extElem.getAttribute(“resource”);   ResourceBundle resBundle =ResourceBundle.getBundle(bundle, getLocale( ));   returnresBundle.getString(resKey);  } }

A TLS field could be used to store the object to simplify calling of theextension element from the XSL code.

The renderer can compile stylesheets and hold them in memory, improvingruntime performance. Each principal stylesheet is compiled and cached inthe Renderer. The cache can be keyed by the brand and name of thestylesheet file. Individual templates, for example, XSL code blocksbetween <xsl:template> elements could be cached. The caching mechanismstores compiled templates and enables access to them by a unique key.This key could be the combined resolved stylesheet file name+templatename. The resolved file name could be computed by logic in aTemplateResolver class. The current “back-off logic” can be retained;e.g., if a template is called from brand://stylesheet.xsl, the systemwould look in the current brand and if not found, then it could look inthe default brand. Following is an example pseudocode for the rendererand resolver:

Renderer.java public class Renderer {   public boolean render(OutputStream os, InputSource is, javax.xml.transform.sax.SAXSourcesource, Map xslParams, String xsltPath, String brand, String protocol,String device, Locale locale)   {     Object stylesheet=getStylesheet(brand, protocol, device, locale, xsltPath);     if(stylesheet != null) {       return processor.process(stylesheet,source, is,os, xslParams);     }     return false;   }   public ObjectgetStylesheet(String brand, String protocol,               Stringdevice, Locale locale, String xsltPath)   {     File f =getStylesheetAsFile(xsltPath, protocol, device);     String key =brand + f.getPath( );     return StylesheetCache.get(key);   } }Resolver.java public class Resolver {   private StringgetStylesheet(String href)     throws FileNotFoundException   {    String brandsToTry[ ] = {m_brand, “default”};     for (int i = 0; i< brandsToTry.length; i++) {       String path =getPathToStylesheet(href, brandsToTry[i]);       File f = newFile(path);       if (f.isFile( ) && f.exists( ))         returnf.getName( );     }    throw new FileNotFoundException( ); } publicSource resolve( String href, String base )    throwsTransformerException {   ... }

In order to support extension elements and replacement of <xsl:import>and <xsl:include>, existing stylesheets can be changed as part of amigration process. For example, occurrences of <xsl:import> and<xsl:include> can be removed altogether. Occurrences of<xsl:call-template> could be replaced with a call to<exslt:call-template name=“foo” href=“file://file-containing-foo.xsl”>.(The ‘href’ attribute may be omitted in cases where the called templateis in the same file.) The system deduces what the ‘href’ value ought tobe. In some cases it could be “file://somefile.xsl”, and in some casesit could be “brand://somefile.xsl”, and in some cases it could be“wap://somefile.xsl”.

There are a few non-principal stylesheets that could contain referencesto global variables. The following example lists English files only:

WEB-INF\templates\m31\default\en\mailfolder\exitcall.xsl WEB-INF\templates\voice\default\en\mailfolder\message_impl.xsl WEB-INF\templates\voice\default\en\mailfolder\newmessage_impl.xsl WEB-INF\templates\voice\default\en\mainmenu\applicationmenu_impl.xsl WEB-INF\templates\voice\default\en\mainmenu\providermenu_impl.xsl WEB-INF\templates\wap\basic\en\mailfolder\calresperror_impl.xslWEB-INF\templates\wap\basic\en\mailfolder\plainmessage.xsl WEB-INF\templates\wap\basic\en\mailfolder\showsubfolder_impl.xslWEB-INF\templates\wap\basic\en\mainmenu\error_impl.xslWEB-INF\templates\wap\basic\en\mainmenu\noaccess_impl.xslWEB-INF\templates\wap\basic\en\mainmenu\pwperror_impl.xslWEB-INF\templates\wap\basic\en\mainmenu\suspended_impl.xslWEB-INF\templates\wap\basic\en\pendingjob_impl.xsl WEB-INF\templates\wap\bbdata\en\mailfolder\calresperror_impl.xslWEB-INF\templates\wap\bbdata\en\mailfolder\plainmessage.xsl WEB-INF\templates\wap\bbdata\en\mailfolder\showsubfolder_impl.xsl WEB-INF\templates\wap\bbdata\en\mainmenu\applicationmenu_impl.xslWEB-INF\templates\wap\bbdata\en\mainmenu\error_impl.xslWEB-INF\templates\wap\bbdata\en\mainmenu\noaccess_impl.xslWEB-INF\templates\wap\bbdata\en\mainmenu\pwperror_impl.xslWEB-INF\templates\wap\bbdata\en\mainmenu\suspended_impl.xslWEB-INF\templates\wap\bbdata\en\pendingjob_impl.xsl WEB-INF\templates\wap\blackberry\en\mailfolder\calresperror_impl.xsl WEB-INF\templates\wap\blackberry\en\mailfolder\plainmessage.xsl WEB-INF\templates\wap\blackberry\en\mailfolder\showsubfolder_impl.xsl WEB-INF\templates\wap\blackberry\en\mainmenu\applicationmenu_impl.xslWEB-INF\templates\wap\blackberry\en\mainmenu\error_impl.xsl WEB-INF\templates\wap\blackberry\en\mainmenu\noaccess_impl.xsl WEB-INF\templates\wap\blackberry\en\mainmenu\pwperror_impl.xsl WEB-INF\templates\wap\blackberry\en\mainmenu\suspended_impl.xslWEB-INF\templates\wap\blackberry\en\pendingjob_impl.xslWEB-INF\templates\wap\up3\en\error\timeout_impl.xslWEB-INF\templates\wap\up3\en\mainmenu\error_impl.xslWEB-INF\templates\wap\up3\en\mainmenu\noaccess_impl.xslWEB-INF\templates\wap\up3\en\mainmenu\pwperror_impl.xslWEB-INF\templates\wap\up3\en\mainmenu\suspended_impl.xslWEB-INF\templates\wap\up3\en\pendingjob_impl.xslWEB-INF\templates\wap\up\en\mailfolder\calresperror_impl.xslWEB-INF\templates\wap\up\en\mailfolder\plainmessage.xsl WEB-INF\templates\wap\up\en\mailfolder\showsubfolder_impl.xsl WEB-INF\templates\wap\up\en\mainmenu\applicationmenu_impl.xslWEB-INF\templates\wap\up\en\mainmenu\error_impl.xslWEB-INF\templates\wap\up\en\mainmenu\noaccess_impl.xslWEB-INF\templates\wap\up\en\mainmenu\pwperror_impl.xslWEB-INF\templates\wap\up\en\mainmenu\suspended_impl.xslWEB-INF\templates\wap\up\en\pendingjob_impl.xsl

These Follow a Similar Pattern:

<xsl:variable name=“isM3L” select=“false( )”/> <xsl:templatename=“blackberry_plainmessage”> ...   <xsl:choose>    <xsl:whentest=“not(boolean($isM3L))”>     ...    </xsl:when>     <xsl:otherwise>     ...     </xsl:otherwise>    </xsl:choose> ...  <xsl:iftest=“$isM3L”>   <card id=“tovoice”>    <p>     <xsl:elementname=“tovoice”>      <xsl:attribute name=“href”>       <xsl:value-ofselect=“...” />      </xsl:attribute>     </xsl:element>

These can be changed during the migration process. Pertinent XSL testswitches (xsl:if, xsl:when, etc.) and a Multimodal Markup Language (M3L)proxy can be removed, with the code resulting in the test evaluation of‘true’ or ‘false’ depending on the value of the ‘isM3L’ variable. Insome non-principal templates the value is always ‘false’, and the testshould be evaluated likewise.

There are a few occurrences of <xsl:apply-templates> in non-principletemplates as follows in which English files are listed:

WEB-INF\templates\voice\default\en\calendarfolder\calendarfolder_impl.xslWEB- INF\templates\voice\default\en\mailfolder\mailfolder_impl.xsl WEB-INF\templates\voice\default\en\mainmenu\providermenu_impl.xsl WEB-INF\templates\wap\basic\en\addressbookfolder\contacts_impl.xsl WEB-INF\templates\wap\basic\en\addressbookfolder\corporatecontacts_impl.xslWEB- INF\templates\wap\basic\en\calendarfolder\calendarfolder_impl.xslWEB- INF\templates\wap\basic\en\mailfolder\mailfolder_impl.xsl WEB-INF\templates\wap\basic\en\mainmenu\applicationmenu_impl.xsl WEB-INF\templates\wap\basic\en\mainmenu\providermenu_impl.xsl WEB-INF\templates\wap\bbdata\en\addressbookfolder\contacts_impl.xsl WEB-INF\templates\wap\bbdata\en\addressbookfolder\corporatecontacts_impl.xsl WEB-INF\templates\wap\bbdata\en\calendarfolder\calendarfolder_impl.xsl WEB-INF\templates\wap\bbdata\en\mailfolder\mailfolder_impl.xsl WEB-INF\templates\wap\bbdata\en\mainmenu\applicationmenu_impl.xsl WEB-INF\templates\wap\bbdata\en\mainmenu\providermenu_impl.xsl WEB-INF\templates\wap\blackberry\en\addressbookfolder\contacts_impl.xsl WEB-INF\templates\wap\blackberry\en\addressbookfolder\corporatecontacts_impl.xsl WEB-INF\templates\wap\blackberry\en\calendarfolder\calendarfolder_impl.xslWEB- INF\templates\wap\blackberry\en\mailfolder\mailfolder_impl.xsl WEB-INF\templates\wap\blackberry\en\mainmenu\applicationmenu_impl.xsl WEB-INF\templates\wap\blackberry\en\mainmenu\providermenu_impl.xsl WEB-INF\templates\wap\up\en\addressbookfolder\contacts_impl.xsl WEB-INF\templates\wap\up\en\addressbookfolder\corporatecontacts_impl.xslWEB- INF\templates\wap\up\en\calendarfolder\calendarfolder_impl.xslWEB-INF\templates\wap\up\en\mailfolder\mailfolder_impl.xsl WEB-INF\templates\wap\up\en\mainmenu\applicationmenu_impl.xslWEB-INF\templates\wap\up\en\mainmenu\providermenu_impl.xsl

Each of these listed cases generally follows a pattern similar to thefollowing:

addressbookfolder\contacts_impl.xsl   <xsl:template name=“up_contacts”>  ...    <xsl:apply-templates mode=“up_contacts”/>    ...  </xsl:template>   <xsl:template match=“a:response” mode=“up_contacts”>    <xsl:if test=“a:propstat/a:prop/a:contentclass[. =‘urn:content-classes:person’]”>      <xsl:element name=“option”>      ...      </xsl:element>    </xsl:if>   </xsl:template>

These cases could to be migrated. There are at least two options:

(1) Inline the code. In essence, replace with:

addressbookfolder\contacts_impl.xsl <xsl:template name=“up_contacts”>... <xsl:for-each select=“a:response”>  <xsl:iftest=“a:propstat/a:prop/a:contentclass[. = ‘urn:content-classes:person’]”>   <xsl:element name=“option”>    ...   </xsl:element> </xsl:if> </xsl:for-each> ... </xsl:template>

(2) Replace <xsl:apply-templates> with <xsl:for-each . .. ><tmon:call-template></xsl:for-each>. In essence, replace the abovewith:

addressbookfolder\contacts_impl.xsl <xsl:template name=“up_contacts”> ...  <xsl:for-each select=“a:response”>   <tmon:call-templatename=“up_contacts_helper”/>  </xsl:for-each>  ... </xsl:template><xsl:template name=“up_contacts_helper”>  <xsl:iftest=“a:propstat/a:prop/a:contentclass[. = ‘urn:content-classes:person’]”>   <xsl:element name=“option”>    ...   </xsl:element> </xsl:if> </xsl:template>

It is possible to append “_helper” to the template name. This can avoidconflicts with existing template already named “up_contacts”.

Both the Renderer and the Extension Element implementation typicallyrequire access to stylesheets, which can be cached after being resolvedand loaded to improve performance. The caching mechanism is abstractedbehind an Interface. The initial implementation of the caching will be astorage and retrieval in a Map. “Smart” caching as described above ispossible. An example of a caching interface is:

public interface StylesheetCache {   Templates get(String brand, Stringprotocol, String device, String xsltPath); }

It is possible to store loaded stylesheets in a Hashtable keyed by thestylesheet's path. The Processor is used to obtain a compiled stylesheetif one was not found in the Hashtable storage.

Simple Stylesheet Cache:

public SimpleStylesheetCache implements StylesheetCache {  privateHashtable m_cache = new Hashtable( );  Templates get(String brand,String protocol, String device, String xsltPath)  {   String path =getPath(brand, protocol, device, xsltPath);   Templates stylesheet =m_cache.get(path);   if (stylesheet == null) {    stylesheet =processor.loadStylesheet(path);    m_stylesheets.put(path, stylesheet);  }   return stylesheet;  } }

The Uniform Resource Identifier (URI) resolver is not required inmigrated templates since they will no longer require xsl:import orxsl:include. They could be removed entirely.

It is also possible to use the system as described for images. An imageis a localizable resource just as a ResourceBundle is. The samealgorithm to resolve a ResourceBundles location can be applied tolocating an image file. Furthermore, a caching scheme could be used tostore the results of the resolution. For example, given a local zh_zn, adefault locale en_us and the extension element could be:

-   -   exslt:getResourceImg path=“a\b\c\images” id=“welcome.gif”>        A resolved image URI cache could be checked in order for the        following keys:

a\b\c\images\zh\zn\welcome.gif a\b\c\images\zn\welcome.gifa\b\c\images\en\us\welcome.gif a\b\c\images\en\welcome.gifa\b\c\images\welcome.gif

For each key, the system can find the key in the cache and the key'svalue could be returned by the extension element. If it does not existin the cache, the file system can be checked if the image file exists.If the file exists in the file system, the key can be written to thecache with a value equal to the key. The previous checked keys can alsobe written to the cache with the same value. For example, ifwelcome_zn.gif is found, then the image URI cache will contain:

a\b\c\images\zh\zn\welcome.gif, a\b\c\images\zn\welcome.gifa\b\c\images\zn\welcome.gif, a\b\c\images\zn\welcome.gifThe template migration could allow all instances of:

-   -   <img src=“a\b\c\images\welcome.gif”/>        to be replaced with:

<exslt:getResourceImage path=”a\b\c\images” id=”welcome.gif”/>

This could be relatively straightforward to execute as a step during themigration process. The image files can be left in the same locations asa result, no migration process is necessary to move or rename the imagefiles.

FIG. 11 is a block diagram showing the relationship between thecomponents in the template rendering (transformation) process afterintroduction of an extension element logic. As illustrated, thefunctional components can be part of a larger server or mobile officeplatform. The renderer 400 is operative with a simple style sheet cache402 and a template processor. An XSLT engine (XALAN) receives inputsfrom the template processor and outputs to the extension element 408,which is operative with the simple style sheet caches. The XSLT enginecan be operative with a URL resolver, 410 which is not required, sincethere is no longer a requirement for <xsl:import> or <xsl:include>. Itmay still be left in place, and thus is depicted in dashed lines. TheExtension Element module is called by the Xalan engine. The Renderer 400pulls the requested template from the Simple Stylesheet Cache 402 andhands to the Template Processor 404 for processing. The TemplateProcessor 404 still has two methods, one to load a template, used by theStylesheet Cache 402 and one for processing a transformation, used bythe Renderer 400. The Stylesheet Cache 402 is separated out into its ownmodule, and is used by both the Renderer 400 and the Extension Element.

FIG. 11A shows another block diagram similar to FIG. 11 of a MOP/server420. The components for rendering a template can include a server 422,renderer 424, cache 426, with an inbox 428 and main cache 430, andextension Java object 432.

In accordance with one non-limiting embodiment, the system supportsmultiple languages and multiple carriers and brands. The MOP code-basecan support these requirements. In previous systems, there had been noformal process, however, for adding new carriers or languages outside ofthe MOP archive, build and push. Updates can be done by pushing out thenew language resource files and new brand specific resource files to theproxies. The system formalizes a process that enables new languages andcarriers to be deployed efficiently without requiring componentrestarts. A system and process is provided for the storage and dynamicdeployment of carrier and language specific resources.

The system meets various functional requirements. It can dynamicallydeploy new languages. It allows a more simple process for deploying anew language bundle to a running installation, without requiring thecomponent to be restarted. This does not include the updating of anexisting carrier or language. The system can dynamically deploy newcarriers. It allows a simple process for introducing a new carrierbundle to a running installation, without requiring the component to berestarted. The system allows a centralized access to a carrier bundle.It can provide a mechanism to retrieve and inspect a carrier bundlethrough a centralized service. Deployment can be centralized via aservice, requiring low human interaction e.g., operations are notrequired to telnet to each proxy in the system and perform some action.

The system has performance, reliability and scalability. There is nosingle point of failure. Resource bundles can be replicated andaccessible from multiple service instances. Additional loads to existingcomponents can be minimized. Additional traffic to the network can beminimized.

The MOP has resource structure that supports a set of java resourcebundles and a set of images (gifs,jpgs). These non-brand specificstrings are stored in different packages, following java resource bundlefile naming conventions for multiple locales.

Resource bundles for XSLT can be located in a package forcom.teamon.resources, containing all text that is resolved at templatetranslation time. Resource bundles for Proxy Injectors can be locatedlogically within the proxy packages that use them, containing alllocalized text that is resolved during action handler execution. Thetext is injected into an XML document, which will be processed by anXSLT to generate localized content.

The following is a non-limiting example of a list of existing non-brandspecific bundles.

com.teamon.proxy.resource\prov.propertiescom.teamon.proxy.resource\proxy.propertiescom.teamon.proxy.html.resource\html.propertiescom.teamon.proxy.html.resource.ppc\prov.propertiescom.teamon.proxy.webdav.bda.resource\bda.propertiescom.teamon.proxy.webdav.davmgmt.resource\davmgmt.propertiescom.teamon.proxy.admin.resource\admin.propertiescom.teamon.proxy.pop.resource\pop.propertiescom.teamon.proxy.wap.resource\wap.propertiesAdditionally, for example, the Tmobile brand can have additionalresource bundles that override three of the common ones listed above:

com.teamon.proxy.resource.tmobile\prov.propertiescom.teamon.proxy.webdav.davmgmt.resource.tmobile\davmgmt.propertiescom.teamon.proxy.resource.tmobile\proxy.propertiesWhen loading a named text string within a named bundle, the system codecan use the following package precedence order to load the string.

-   -   1. com.teamon.proxy.[app].resource.[device].[bundle]    -   2. com.teamon.proxy.[app].resource.[brand].[bundle]    -   3. com.teamon.proxy.[app].resource.[bundle]    -   4. com.teamon.proxy.resource.[device].[bundle]    -   5.        com.teamon.proxy.resource.[brand].[bundle]com.teamon.proxy.resource.[bundle]

A brand can be formed as templates, images, java resource bundles andterms and conditions. Brand resources can be located within theconfigured brand directory, under which there is a particularsubdirectory for each brand e.g. [BrandDir]\tmobile.

Templates can be defined. A particulate brands subdirectory (e.g.tmobile) contains subdirectories for each application (e.g. html) underwhich there may be one or more device subdirectories (e.g. blackberry).Templates found in these directories will override those found in theconfigure template directory. They may also exist additional templatesthat extend the base application functionality (of course this impliesnew actions/code. There are images within the brand's directory there isa single image directory called “images” containing localized images.Java Resource Bundles can be included. A brand may override certainproxy injected strings by providing a brand specific bundle.

Currently localized terms and conditions for the wireless communicationsdevice provider and the carrier are located within a Direct Access (BDA)subdirectory of the brand. Each terms and conditions is a text file witha hardcoded names, e.g.:

[branddir]\[brand]\bda\en\termsandconditions.txt[branddir]\[brand]\bda\en\carriertandc.txt

Each brand can be configured, in the database, with a particular scheme.Schemes are located with a proxy configured scheme directory. Schemedirectories contain non-localized cascading stylesheet (CSS) files, andlocalized images. Schemes may be shared by multiple brands.

A Resource Deployment Package (RDP) can be used to deploy any number oflanguages and/or carriers/brands. Each deployment package containsenough information to identity its contents and deployment instructions.

The RDP can be likened to a jar, which contains language and/or carrierresources. The jar allows the system to organize the resources andcompress them for efficient deployment. The RDP contains a descriptorfile and a set of resource jars. The descriptor file containsinformation about each resource jar to be deployed. A resource jarcontains all the resources for a particular language or carrier andcontains the path information so it can be easily expanded into theresource consumers file system. FIG. 12 shows a RDP at 500 that includesa description 502 with references to French language 504, Germanlanguage 506 and a Verizon or Carrier file 508 as a non-limitingexample.

The descriptor file contains XML, which contains deployment informationfor each resource jar within the RDP. An example of the schem of the RDPdescriptor file is:

<?xml version=“1.0” encoding=“utf-8” ?> <xs:schema targetNamespace=“”xmlns:xs=“http://www.w3.org/2001/ XMLSchema”>  <xs:elementname=“package”>   <xs:complexType>    <xs:sequence>     <xs:elementname=“Resource”>      <xs:complexType>       <xs:attribute name=“id”type=“xs:ID” />       <xs:attribute name=“type” type=“ResourceType” />      <xs:attribute name=“jar” type=“xs:string” />       <xs:attributename=“description” type=“xs:string” />       <xs:attributename=“dirPropKey” type=“xs:string” />      </xs:complexType>    </xs:element>    </xs:sequence>   </xs:complexType>  </xs:element> <xs:simpleType name=“ResourceType”>   <xs:restriction base=“xs:string”>   <xs:enumeration value=“language” />    <xs:enumerationvalue=“carrier” />   </xs:restriction>  </xs:simpleType> </xs:schema>

A resource element describes one resource jar within the RDP, and canhave the following attributes:

Attribute Type Description id ID Uniquely identifies a resource jar.Each version of a particular language or carrier resource jar shouldalways have the same id e.g. Each version of the French languageresource jar should always have the same id. type ResourceType Thisvalue should either be “language” or “brand”. jar string The name of theresource jar within the RDP. description string A human readable stringdescribing the resource jar e.g. “French Language” dirPropKey string Thename of the property who's value is the name of the directory in whichthe resource consumer should expand the jar into e.g.“com.teamon.proxy.schemes”

An example descriptor.xml for the language French follows.

<package>  <resource id=”lang-fr” type=”language” jar=”fr” description=”French”   dirPropKey=”teamon.proxy.resources.dir”/> <resource id=”lang-fr-tmo” type=”language” jar=”fr-tmobile”  description=”French TMobile” dirPropKey=”teamon.proxy.resources.dir”/> </package>

An example descriptor.xml for the carrier/brand verizon follows.

<package>  <deploy type=”brand” id=”br-verizon” jar=”verizon”desc=”Verizon  wireless”   dirProp=”teamon.proxy.brand.directory”/></package>

An example RDP contents for the French language follows.

rdp001.jar  descriptor.xml  fr.jar   admin_fr.propertiescom.teamon.resources   bda_fr.properties com.teamon.resources  blackberry_fr.properties com.teamon.resources   calendar_fr.propertiescom.teamon.resources   common_fr.properties com.teamon.resources  defaultbrand_fr.properties com.teamon.resources  tmobile_fr.properties com.teamon.resources  fr-tmobile.jar  prov.properties com.teamon.proxy.resource.tmobile   davmgmt.propertiescom.teamon.proxy.webdav.davmgmt.- resource   .tmobileproxy.properties  proxy.propertiescom.teamon.proxy.resource.tmobile

The following use cases can be implemented as non-limiting examples.

-   -   1. New Resources: A new language or carrier needs to be added to        the system.    -   2. Added component: A new instance of a component is added to        the system, it has little or no resources, it must be able to        retrieve any missing resources.    -   3. Re-started component: A component is down and re-started.        While down it missed one or more new resource notifications. It        must now get those resources.    -   4. Where is my brand: If an account is of carrier/brand X and        that brand's resources are not present, then they are retrieved.    -   5. Updated Resources: A language or carrier resource has been        modified requiring a resource to be redeployed, during running        system or maintenance.    -   6. Version consistency across components: If a new version of a        resource is introduced, we should make sure that we do not end        up with different instances having different versions of        resources.

An external system/process can provide an RDP to a resource deploymentservice within the IS system. That component makes available theresources to ensure that each component of the system is made aware ofthe resource. To ensure a timely push of the resource those componentsmust be notified of the resource's existence or be polled often enoughto be timely. Notifications would require that each interested party isknown. Polling would require more network resources. However, with apurely polling approach there may be no need for a Primary DeploymentService.

Whenever a component is added to the system or has been re-started,there exists a chance that it does not have the required resources. Inthis case the component should be able to synchronize with the currentlydeployed updates. Such a process can be used to update resources duringmaintenance windows (shutdowns), when re-starting from a failure, when abrand resource is missing or if polling is employed for new resourcedetection.

A given resource should not differ from one component to another. Sinceit is not a requirement to update resources on the fly and because thesystem uses java resource bundles, which do not provide a refreshmechanism, once a particular resource is deployed, an updated resourcetypically should not be available. The only way to update a resourcewill be during system down times via a specific mechanism.

There now follows a description of the components and process ofdeploying an RDP.

FIG. 13 illustrates a non-limiting example of the components involved inresource deployment and a typical high level process flow for a resourcepush. The basis components are shown as a pooled service 600, which isoperable with a deployment service 602 and cache 604, and data store606. A deployment service can include primary, secondary and “cache”only. When a resource consumer has been notified of a new resource orhas determined via a synchronization process that it needs to retrieve aresource, it connects to a deployment service via load balancer (Big IP)that will load balance the request to one of the deployment services. Aprimary deployment service 608 receives signals from an RDP 610 asillustrated. The pooled service 600 is operable with the deploymentservice 602. Three proxies 614, 616, 618 are operable with the pooledservice 600. Two directories 620, 622 are shown and can be deployed withthe service.

An example of a set of sequence steps follow.

-   -   1. An RDP is constructed and sent to the Primary Deployment        Service.    -   2. The Deployment Service saves the resources in the RDP to the        database.    -   3. The Deployment Service notifies all interested proxies of the        new resources.    -   4. The Proxy retrieves the resource via the pooled deployment        service.    -   5. The deployment service checks its cache for the requested        resource and if not available retrieves from the DB and caches        it. Lastly the resource in returned.

The proxy deploys the resource.

At some point, an RDP is created, which will then be sent to the PrimaryDeployment Service (DS), perhaps via a console, script or utilityapplication. Two mechanisms could be considered for delivery of the RDPto the Primary DS:

-   -   (1) The client tool recopies the RDP to a known deployment        directory. The Primary DS detects the RDP and begins the        deployment process; and    -   (2) The client tool uses a WebDav interface implemented by the        Deployment Service to send the RDP, which starts the deployment        process.

The Deployment Service (DS) is responsible for receiving RDPs,Persisting resources, notifications to interested components, retrievingresources, and providing synchronization info. Basic non-limitingcomponents are illustrated in FIG. 14, for example, the Deploymentservice 700, with a cache 702, WebDAV 704 and registry 706 and container708, and database 710.

The container 708 provides an environment for the DS to execute. In thiscase, a Soap Servlet is the most likely candidate as it can provide anHTTP listener for WebDAV request and a pool of DB connections. Since itis a pooled resource, the DS becomes a pooled resource as well.

The cache stores resources locally with the service. If the requestresource does not exist in the cache then it is retrieved from the DB.The resources are stored in a configured directory as RDP's. An index isalso created that tracks which resources are in the cache. The cachealso provides a mechanism that returns a set of existing resources,which will require a query to the DB. This will enable synchronizationrequest to be processed.

The container is configured to route WebDAV request to the DS. TheWebDAV component processes the request, which can be one of three:

-   -   (1) Put RDP. Stores RDP in local cache and in the DB. Notifies        registry.    -   (2) Retrieve Resource. Given a resource key the resource is        retrieved.    -   (3) Synchronize. Prop Find on root folder returns a list        identifying available resources. The list will include the        resources id and its version id. The client will use this info        to determine which resources it must download.

Each component interested in receiving new resources, must register withthe Primary DS. Registration is merely keeping a socket open via whichnotifications can be sent. A notification will consist of a WebDAV URIto retrieve an RDP. The client should use a scheme similar to the PDS toswitch from a primary to secondary DS.

The Central database is used to persist and propagate resourceson-demand to other DS instances. A Resource table(s) can be created thatstores the following information:

Name Type id (unique, key) 64 chars? versioned long RDP (? Darren) Thisis just a single jar with a descriptor file, or descriptor values shouldbe added to this table.

Stored procedures can be created to store a resource, to retrieve aresource and to retrieve a list of all resources.

Each resource consumer, such as the proxies, has the followingresponsibilities.

-   -   (1) Synchronize resources at startup.    -   (2) Maintain a registry of deployed resources.    -   (3) Listen for resource notifications.    -   (4) Retrieve resources and deploy.

Updated resources should only be deployed at scheduled maintenanceperiods where resource consumers will be stopped and started. If anupdated component is introduced otherwise, it may cause differentversions of the same resource to be in-use at the same time. Thefollowing steps should be taken to update resources.

-   -   (1) Stop the service    -   (2) if using rcopy solution then goto step 6    -   (3) Start PDS    -   (4) Send via WebDAV updated RDPs    -   (5) Goto 8    -   (6) Rcopy RDPs to Primary DS directory    -   (7) Start PDS    -   (8) Restart components, which will now synchronize content.

During synchronization at startup, fail to start if cannot findsynchronize. Separate servlet within Soap servlet. Enumerate negs andpos.

An example of a handheld mobile wireless communications device 1000 thatmay be used is further described in the example below with reference toFIG. 15. The device 1000 illustratively includes a housing 1200, akeypad 1400 and an output device 1600. The output device shown is adisplay 1600, which is preferably a full graphic LCD. Other types ofoutput devices may alternatively be utilized. A processing device 1800is contained within the housing 1200 and is coupled between the keypad1400 and the display 1600. The processing device 1800 controls theoperation of the display 1600, as well as the overall operation of themobile device 1000, in response to actuation of keys on the keypad 1400by the user.

The housing 1200 may be elongated vertically, or may take on other sizesand shapes (including clamshell housing structures). The keypad mayinclude a mode selection key, or other hardware or software forswitching between text entry and telephony entry.

In addition to the processing device 1800, other parts of the mobiledevice 1000 are shown schematically in FIG. 15. These include acommunications subsystem 1001; a short-range communications subsystem1020; the keypad 1400 and the display 1600, along with otherinput/output devices 1060, 1080, 1100 and 1120; as well as memorydevices 1160, 1180 and various other device subsystems 1201. The mobiledevice 1000 is preferably a two-way RF communications device havingvoice and data communications capabilities. In addition, the mobiledevice 1000 preferably has the capability to communicate with othercomputer systems via the Internet.

Operating system software executed by the processing device 1800 ispreferably stored in a persistent store, such as the flash memory 1160,but may be stored in other types of memory devices, such as a read onlymemory (ROM) or similar storage element. In addition, system software,specific device applications, or parts thereof, may be temporarilyloaded into a volatile store, such as the random access memory (RAM)1180. Communications signals received by the mobile device may also bestored in the RAM 1180.

The processing device 1800, in addition to its operating systemfunctions, enables execution of software applications 1300A-1300N on thedevice 1000. A predetermined set of applications that control basicdevice operations, such as data and voice communications 1300A and1300B, may be installed on the device 1000 during manufacture. Inaddition, a personal information manager (PIM) application may beinstalled during manufacture. The PIM is preferably capable oforganizing and managing data items, such as e-mail, calendar events,voice mails, appointments, and task items. The PIM application is alsopreferably capable of sending and receiving data items via a wirelessnetwork 1401. Preferably, the PIM data items are seamlessly integrated,synchronized and updated via the wireless network 1401 with the deviceuser's corresponding data items stored or associated with a hostcomputer system.

Communication functions, including data and voice communications, areperformed through the communications subsystem 1001, and possiblythrough the short-range communications subsystem. The communicationssubsystem 1001 includes a receiver 1500, a transmitter 1520, and one ormore antennas 1540 and 1560. In addition, the communications subsystem1001 also includes a processing module, such as a digital signalprocessor (DSP) 1580, and local oscillators (LOs) 1601. The specificdesign and implementation of the communications subsystem 1001 isdependent upon the communications network in which the mobile device1000 is intended to operate. For example, a mobile device 1000 mayinclude a communications subsystem 1001 designed to operate with theMobitex™, Data TAC™ or General Packet Radio Service (GPRS) mobile datacommunications networks, and also designed to operate with any of avariety of voice communications networks, such as AMPS, TDMA, CDMA, PCS,GSM, etc. Other types of data and voice networks, both separate andintegrated, may also be utilized with the mobile device 1000.

Network access requirements vary depending upon the type ofcommunication system. For example, in the Mobitex and DataTAC networks,mobile devices are registered on the network using a unique personalidentification number or PIN associated with each device. In GPRSnetworks, however, network access is associated with a subscriber oruser of a device. A GPRS device therefore requires a subscriber identitymodule, commonly referred to as a SIM card, in order to operate on aGPRS network.

When required network registration or activation procedures have beencompleted, the mobile device 1000 may send and receive communicationssignals over the communication network 1401. Signals received from thecommunications network 1401 by the antenna 1540 are routed to thereceiver 1500, which provides for signal amplification, frequency downconversion, filtering, channel selection, etc., and may also provideanalog to digital conversion. Analog-to-digital conversion of thereceived signal allows the DSP 1580 to perform more complexcommunications functions, such as demodulation and decoding. In asimilar manner, signals to be transmitted to the network 1401 areprocessed (e.g. modulated and encoded) by the DSP 1580 and are thenprovided to the transmitter 1520 for digital to analog conversion,frequency up conversion, filtering, amplification and transmission tothe communication network 1401 (or networks) via the antenna 1560.

In addition to processing communications signals, the DSP 1580 providesfor control of the receiver 1500 and the transmitter 1520. For example,gains applied to communications signals in the receiver 1500 andtransmitter 1520 may be adaptively controlled through automatic gaincontrol algorithms implemented in the DSP 1580.

In a data communications mode, a received signal, such as a text messageor web page download, is processed by the communications subsystem 1001and is input to the processing device 1800. The received signal is thenfurther processed by the processing device 1800 for an output to thedisplay 1600, or alternatively to some other auxiliary I/O device 1060.A device user may also compose data items, such as e-mail messages,using the keypad 1400 and/or some other auxiliary I/O device 1060, suchas a touchpad, a rocker switch, a thumb-wheel, or some other type ofinput device. The composed data items may then be transmitted over thecommunications network 1401 via the communications subsystem 1001.

In a voice communications mode, overall operation of the device issubstantially similar to the data communications mode, except thatreceived signals are output to a speaker 1100, and signals fortransmission are generated by a microphone 1120. Alternative voice oraudio I/O subsystems, such as a voice message recording subsystem, mayalso be implemented on the device 1000. In addition, the display 1600may also be utilized in voice communications mode, for example todisplay the identity of a calling party, the duration of a voice call,or other voice call related information.

The short-range communications subsystem enables communication betweenthe mobile device 1000 and other proximate systems or devices, whichneed not necessarily be similar devices. For example, the short-rangecommunications subsystem may include an infrared device and associatedcircuits and components, or a Bluetooth™ communications module toprovide for communication with similarly-enabled systems and devices.

Many modifications and other embodiments of the invention will come tothe mind of one skilled in the art having the benefit of the teachingspresented in the foregoing descriptions and the associated drawings.Therefore, it is understood that the invention is not to be limited tothe specific embodiments disclosed, and that modifications andembodiments are intended to be included within the scope of the appendedclaims.

1-21. (canceled)
 22. A system for rendering presentation pages,comprising: a server configured to render at least one resourceincluding at least one of a image and text, into a presentation pagebased on a language requirement at a foreign locale; a proxy configuredto deploy the at least one resource to the server; and a deploymentservice configured to save to the at least one resource and notify theproxy of at least one new resource for deployment.
 23. The systemaccording to claim 22, wherein the server is configured to render apresentation page into localized content based on locale.
 24. The systemaccording to claim 23, further comprising resource bundles for at leastone of localized images and text that are rendered into an XML documentto be processed by the extensible stylesheet transformer to generatelocalized content.
 25. The system according to claim 23, wherein thelocalized content comprises content in a foreign language used at thelocale.
 26. The system according to claim 22, wherein the server isconfigured to operate using a JAVA extension.
 27. The system accordingto claim 22, wherein the server is configured to render an HTMP or WAPoutput.
 28. The system according to claim 22, wherein the servercomprises a web server.
 29. The system according to claim 22, whereinthe server comprises an electronic mail (email) server.
 30. The systemaccording to claim 22, wherein the server is configured to store aplurality of resource deployment packages (RDPs), each RDP comprisingdeployment content based on locale.
 31. A system for renderingpresentation pages, comprising: a mobile wireless communications device;a wireless communications network; and a mobile office platformconfigured to communicate with the mobile wireless communications deviceover the wireless communications network, the mobile office platformcomprising a server configured to render at least one resource includingat least one of a image and text, into a presentation page based on alanguage requirement at a foreign locale, a proxy configured to deploythe at least one resource to the server, and a deployment serviceconfigured to save to the at least one resource and notify the proxy ofat least one new resource for deployment.
 32. The system according toclaim 31, wherein the server is configured to render a presentation pageinto localized content based on locale.
 33. The system according toclaim 32, further comprising resource bundles for at least one oflocalized images and text that are rendered into an XML document to beprocessed by the extensible stylesheet transformer to generate localizedcontent.
 34. The system according to claim 33, wherein the localizedcontent comprises content in a foreign language used at the locale. 35.The system according to claim 32, wherein the extensible stylesheetextension comprises a JAVA extension.
 36. The system according to claim32, wherein the server is configured to render an HTMP or WAP output.37. The system according to claim 32, wherein the server comprises a webserver.
 38. The system according to claim 32, wherein the servercomprises an electronic mail (email) server.
 39. The system according toclaim 32, wherein the server is configured to store a plurality ofresource deployment packages (RDPs), each RDP comprising deploymentcontent based on locale.
 40. A method for rendering presentation pagescomprising: operating a server to render at least one resource includingat least one of a image and text, into a presentation page based on alanguage requirement at a foreign locale; operating a proxy to deploythe at least one resource to the server; and operating a deploymentservice to save to the at least one resource and notify the proxy of atleast one new resource for deployment.
 41. The method according to claim40, comprising operating the server to render a presentation page intolocalized content based on locale.
 42. The method according to claim 40,comprising storing a plurality of resource deployment packages (RDPs),each RDP comprising deployment content based on locale.